BBS Toolkit

home *** CD-ROM | disk | FTP | other *** search

/ BBS Toolkit / BBS Toolkit.iso / pc_board / 2act23.zip / 2ACT.DOC < prev next >

Wrap

Text File | 1991-11-30 | 53KB | 1,285 lines

Second Account copyright 1991 by Dalaye Gabriel Polymath One BBS, of Trenton, NJ (609) 392-5953 CIS 70017,1667 Seamless interface to allow leaving PCBoard, loading a second copy of PCBoard, with the proper User info being loaded without User input. Intended to allow a Sysop to use a second Users file for separate account access, including the use of aliases, and even a separate Cnames file to allow different conference access, and any other PCBoard configuration files (Tcan, Pwrd, Upsec, etc.). This is expected to be used only with PCBoard versions of 14.0 and higher. Future versions may require the use of PCBoard versions of 14.5a or newer. Use of MS-DOS 3.30 or newer, is required. All modem initialization and control is maintained by the first loaded copy of PCBoard. Fully functioning while not registered, only user display control is inhibited.Contents: Introduction ........................ 1 Method ........................ 1 Features ........................ 2 License to Use and Distribute ......... 3 Why Second Account .................... 4 Solution .................... 5 Security .................... 6 New Since Its First Release ......... 7 Quick Set-Up .................... 8 Set-Up .................... 9 Files Included in the 2ACT##.ZIP ...... 11 Files that will be Created by 2ACT.ZIP . 11 Miscellaneous .................... 11 Files Detail .................... 12 Description .................... 13 2ACT.CFG .................... 16 2ACTADD.EXE .................... 19 1STTIME .................... 20 Board Files .................... 21 OFF .................... 23 Errors .................... 23 Maintenance .................... 24 Available Command for Maintenance ..... 24 Applications .................... 26 Questions and Answers ................. 31 Introduction: This text makes reference to all in the male gender for the sake of brevity, but in all cases this refers to both male and female. This text is not complete on setting up doors, or a copy of PCBoard. It is assumed you have purchased PCBoard and have all needed docs on proper BAT files, and the use of PCBSETUP.EXE, MKTXT145.EXE and other required support files from Clark Development. This program requires access to BRUN45.EXE, the "patched" version, so your users are not disconnected. 2ACT has been installed on single and multi-nodes systems, with DesqView and under LANtastic. Multiple copies of 2ACT are in use on a single BBS, and doors are properly accessed while in 2ACT. 2ACT is not a door, but a utility, accessed via a door. Method: Read PCBOARD.SYS file, creating a new PCBOARD.SYS in new sub-dir with all changes needed to properly access a second (and different) USERS file than the first PCBOARD.SYS refers to. This requires accessing the following files from area leaving: PCBOARD.SYS, Users. And accessing the following files for the new PCBoard area: PCBOARD.SYS, USERS, PWRD. It will write a new BAT file, 2ACT$.BAT called from the first account (from the PCB written DOOR.BAT) The user is always placed in Conference 0 upon entry via 2ACT. All major functions occurring during 2ACT processing will be written to the specified CALLERS file. New users entering the Second Account will automatically be entered based upon sysop configuration. Features: ALL PCBOARD INTEGRITY MAINTAINED! PCboard security is responsible for virtually all Sysop control over Second Account access Carrier Loss, Modem Speed, Networking, Inactivity, Security Levels, etc ALL are limited only by PCBoard and the Sysop - NOT this program Fast, seamless, with NO interaction required by the User after the first time ever in Second Account! Unlimited Conferences and access control actual possibilities by the Sysop are VIRTUALLY UNLIMITED - No computer has yet been built that can be configured for all of them at one time!) - the only real limit is Sysop imagination. NO MENUS OR NOTICES DISPLAYED TO USER (except 1 short sentence at run time - not even that, in some instances) - SEAMLESS!! Sysop Alias? No problem! NO User prompting for Alias! Seamlessly loaded by Second Account! Allows sharing of 100% of the PCBoard files (except PCBoard.sys) with first account if so desired Allows Second Account to load a separate Users file, separate PCBOARD.DAT, CNAMES, PWRD, PCBTEXT, BRDM (and anything else!) if desired to allow different conferences, file access, menus, aliases, security levels, files ratios, and anything else you can dream up. Separate maintenance program for LOCKing out, or ALLOWing (or disALLOWing) individual Users to the Second Account All maintenance to actual second account Users via PCBoard only. Sysop record 1 security Can be configured as entirely INVISIBLE to Users not-Sysop defined Fully functional while Unregistered, just not seamless nor invisible License to Use and Distribute: PCBoard is a registered trademark of Clark Development Corp, and all reference to such is here to identify their software, and the proper expected use of Second Account in conjunction with such software. All programs released relative to Second Account, including, but not limited to 2ACT.EXE, 2ACTCVT.EXE, 2ACTADD.EXE, 2ACTSM.EXE are copyrighted by Dalaye Gabriel, and all rights are reserved by the author. No alterations may be made in any manner to the distributed group of files composing the Second Account package except by the author, either individually or as a whole. Anyone has the right to distribute unaltered copies of the entire Second Account package as a whole, without further permission. The Second Account package is released without a warranty for any specific purpose whatsoever, and anyone using any portion of this software package has no claim upon the author for damages, and uses such software at his/her own risk. All software is distributed freely through Bulletin Board Systems and no person or company is allowed to charge any fee for distributing any portion of the Second Account package without separate license from the author. Under US copyright law, full compensation, including all legal fees incurred, will be recovered from violators of this license. The only acceptable fee under this license is any amount required for only diskette and postage costs when distributed in such manner by any not-for-profit group, whether a computer User's Group, or a public Bulletin Board System. No compensation for service or labor to provide diskette copies is allowed under this license. No use is allowed of Second Account on any system for a period of more than 45 days of evaluation without registration. It is distributed under the "shareware" concept, to allow a proper trial period before registering, and is not free software, nor in the public domain. Why Second Account? My BBS has considerable adult and non-adult traffic of Users, and I found it best to entirely segregate the two areas. I'm aware that many merely open a second BBS. Meanwhile, any users visiting the adult conferences wish to use aliases to leave messages. I tried another alternative, but was I wasn't happy with its operation, or the idea I could do little to control access as I chose to. Meanwhile, I found it nice to segregate credits of Uploads/Downloads to a users record from the 2 areas, and seriously considered doing what so many people eventually do: open a second, adults-only BBS, leaving the first alone. I considered this unacceptable, as it would mean more work for the user to visit both, and tie up all my equipment separately, stop node chats, and other such. So, I found it best to create a new sub-directory, one for each node on the system, and setup a separate BBS entirely, but, to be accessed as a door from the first BBS. This wastes very little disk space, as most files can be shared with the first. The problem with initially calling the second board from the first? Users hated the idea of having to logon a second time, and I hated the maintenance headache of seeing who opened a second account in the second board loaded, as, when it prompts for a name, more than 1 user chose to open new additional accounts for himself. Major headache as the number of users grew! Solution: Second Account! It lets you set up a second BBS as a door from the first BBS, loading all user information needed with the information you configure within the 2ACT.CFG file. 2ACT.CFG must be in the sub-directory that 2ACT is called from. Many users of this software will enjoy the tremendous flexibility it now gives a PCBoard Sysop. The first account that users log on to the BBS with can now be used as a "front end" to cleanly load additional accounts, which need not share any information with the first, or share as much as desired. Some configurations take extremely little additional disk space, and allow the Sysop literally twice the possible configurations for a single BBS as compared to the already enormous number allowed under PCBoard! The Sysop may choose to actually run an entirely separate BBS as a Second Account, with no time constraints being shared, or files, and even the Sysop responsibilities need not be shared. Imagine running 2 (or more!) entirely separate Bulletin Board Systems from the same phone line, and still maintaining the complete security of PCBoard! And, the user only needs one logon per phone call! My BBS now runs several sub-boards in this manner, each a Private BBS for a separate purpose. Example: A software author provides support on my BBS to registered users of his software. Prior to the use of Second Account, the Sysop (me) had to assign certain levels and do the maintenance of the Support Conference involved. Now, the entire job is under that author's control, and his registered users are placed by him, and can freely upload, download and read messages with no impact upon their time or status on the "normal" BBS! Security: Record #1 of the USERS file (second account) can only be accessed by record #1 of first account USERS file. In no place is the Sysop password checked for or written by this program. LOCK and ALLOW features are now available, letting the Sysop run this program with ability to LOCK anyone not entered by him, or to LOCK individual users from access. The ALLOW feature is similar to LOCK, but lets the Sysop have a more polite method of not allowing a User access to the Second Account than LOCK would be used for. It is meant to be used where a Sysop chooses to allow a New User to the Second Account, but must review his status before actual access allowed. Using LOCK and ALLOW combined with the security of PCBoard gives the Sysop tremendous flexibility in controlling access as he sees fit. All normal PCBoard security remains in full force, as this program does not supercede PCBoard, but merely allows the PCBoard security to take over. Any unusual occurences are handled almost entirely by the exisiting (and well-proven) PCBoard software. Please read elsewhere about the value of the "dummy PCBoard.sys" file if you have non-modem Users on your system - this should be taken into account by any such Sysop not using the PCBoard parameter of checking for a User's Password upon return from a Door. Properly setup, the loss of carrier detect handles such situations where modems are in use. New Since Its First Release: Ability to force Users to read NEWS, messages etc the first time accessing the Second Account each day. The word PCBoard has been dropped, and the PCB prefix has been dropped to insure no conflict with the trademark "PCBoard" of Clark Development, and to insure no one receives any impression that this program is endorsed by the authors of PCBoard. Better documentation! File holds 1st Account & 2nd Account User Names, and flags to control access to the Second Account Writes all important occurrences to the CALLERS file. Better security, including self-check. Automatically can add New Second Account Users for access! Separate maintenance program to control access to the Second Account Very good error-trapping capabilities Sysop definable messages for LOCKed out Users Can enter any New User in for access to the Second Account without requiring the Sysop to do anything at all What's Coming in the Future? 2ACTSM.EXE will be accessable without the use of Doorway More flexibility of control of User time allowances ... and at this time any ideas of Users will be considered. Quick Set-Up: This is for everyone that hates to read through the documentation, and is not recommended for anyone not fully aware of how to setup PCBoard. All references here, and changes to included files in the ZIP, assume you will be using 2ACT for an Adults area, with separate USERS and PWRD files. This is for one node only. 1) Create a new sub-directory (C:\PCB\ADULT) 2) Copy your current PCBOARD.DAT, CNAMES, CNAMES.@@@ to it 3) Run PCBSETUP.EXE in there, defining the new location for the CNAMES, PCBOARD.DAT, USERS, and PWRD files. You may also wish to use that new sub-directory to place separate TCAN, FSEC, and UPSEC files, depending on your use. Change all reference to adult specific files to that a area, including PCBTEXT. REMOVE ALL MODEM INITIALIZATION AND CONTROLS from the new PCBOARD.DAT, and answer Y to Drop to DOS after each call. Edit the PWRD, FSEC, UPSEC, TCAN files as you see fit. 4) Place all the files from the 2ACT ZIP in the new sub- directory 5) Run PCBSM and place your sysop alias in record 1 6) Edit the 2ACT.CNF file to reflect your proper sub- directories (you may want to review page ## to set user access also) 7) Run 2ACTSM to initialize the 2ACT.NAM file 8) Edit the first account's DOORS.LST file to add the new "door" and the DOORS menu (suggested to name it ADULTS). 9) Copy the enclosed SECOND file to your main PCB directory, and edit it to reflect proper paths to files, and rename it to ADULTS if using it as expected. 10) If using Doors from this area, the ADULTS.BAT will have to be altered to also have proper sub-directories, to return to the Adults Board after the door has been exited 11) Try it out! If you like it... Please register, and you can have more seamless operation, and the latest version sent to you - including version 3.0 when released (100% seamless - no displays to users) Set-up: It is assumed the Second account will not share 100% of the files with the first account, and a separate sub-directory will be used for all files particular to each Second account (and node) in use. If you expect to use more than one Second Account, decide all the parameters for each carefully for getting started - the possible layout of individual access becomes virtually limitless. Read the section on Applications prior to setting up for some guidelines. These set-up procedures are for the most common, and simple, use of PCB Second Account, which is the first defined under Applications. Create a sub-directory: C:\PCB\SECOND suggested name Most likely, you will be sharing most parameters and files with the first account, so copy that account's CNAMES.* and PCBOARD.DAT file to C:\PCB\SECOND\ If only minor changes are expected in any of the account specific files, copy those over also at this time. Run PCBSETUP.EXE and change the parameters for file location for the files to be located for only this Second Account. Expected to be: USERS, CNAMES, BRDM, PCBTEXT, TCAN And possibly: DOWNLOAD.TXT, PWRD, UPSEC And anything else you feel should be account specific. If you wish to use an Alias as Sysop, place that Alias in Record #1 of the Users file, and set the "Use Real Name?" flag to Y. If to run under multiple nodes, create a separate sub-directory for each node, as: C:\PCB\SECOND2 for Node 2, etc. Copy the PCBOARD.DAT from C:\PCB\SECOND to each nodes second account sub-directory, and run PCBSETUP to change node specific parameters. It is assumed no other files will exist in this sub-directory other than BAT files required for file transfer, or possibly EVENT.SYS and such. Copy all the 2ACT files to your C:\PCB\SECOND sub-directory. Edit the 2ACT.CFG to relect your requirements. If additional nodes will be used, copy the 2ACT.CFG to nodes new sub-directory also (ie: C:\PCB\SECOND\NODE2) and edit that copy to show the proper files locations for that node. Run 2ACTSM (or 2ACTCVT if upgrading from ver.1.1) to initialize the 2ACT.NAM file. No entry required for the Sysop in this file, but you may wish to enter a User (or many) at this time depending on your configuration. Edit your Doors.1st file to include 2ACT as a door, and then place it in your Doors Menu. Edit the 2ACT file to use the parameters required for your system. If multi-node, then copy it to each nodes first PCBoard directory, and edit each to reflect what is needed to access the proper node's sub-directory. Done! Files Included in the 2ACT##.ZIP: 2ACT.EXE - The main Second Account program 2ACT.CFG - Configuration file, must be edited for your system 2ACTCVT.EXE - Program to build 2ACT.NAM from your Comment2 fields if previously running an older version of 2ACT. 2ACTADD.EXE - Program to add new users to the 2ACT.NAM file automatically 2ACTSM.EXE - Maintenance program for 2ACT.NAM file NOGOOD.MSG - Message shown to User when unrecoverable error occurs NEWGUY.MSG - Message to be displayed to a new Second Account User NOTALLOW.MSG - Message to show a User flagged as Not ALLOWed LOCKED.MSG - Message to be shown to a LOCKed out User 2ACT - Example of a calling BAT file to run 2ACT SECOND.BAT - Example of BAT to reload from a Door ANYDOOR - Example of how to run a Door from the second account, and to properly return to the second account PCBSYS.HLD - An "empty" PCBoard.sys file you may choose to use for security reasons KEYSTUFF - example file to force NEWS reading once per day Files that will be created by 2ACT: 2ACT.NAM - Stores first account & second account names, and the lock and allow flags for each user NOGOOD. - 0 byte file created if 2ACT cannot handle the user for any reason not covered elsewhere This filename can be changed by an entry in 2ACT.CFG NEWGUY. - 0 byte file created when a user with no entry in the 2ACT.NAM file enters This filename can be changed by an entry in 2ACT.CFG 1STTIME - 0 byte file created if the User is entering the Second Account for the first time that day This filename can be changed by an entry in 2ACT.CFG Miscellaneous: It is assumed in the examples that you have a file called BOARD.BAT that will load the first account, with all proper checks for event and door use. Files Detail: 2ACT - File to be opened as a Door by PCBoard, it must be defined in Doors.Lst cd\pcb\second if exist 2act$.bat del 2act$.bat if exist endpcb del endpcb if exist door.bat del door.bat if exist newguy del newguy if exist nogood del nogood c:\util\2act rem if exist newguy goto end rem if exist nogood goto end if exist 1sttime copy keystuff pcbstuff.kbd call 2act$.bat if not exist newguy goto done c:\util\2actadd :done if exist door.bat door if exist event.bat event if exist endpcb goto end second :end copy pcbsys.hld pcboard.sys c: cd\pcb board Description - Notice that if 2ACT fails to properly build the BAT file to load the second PCB account, it will definitely return to the first account. Also, you may want to include the line to copy a "dummy" PCBoard.sys (included) prior to reloading the first account in case there is an error of any sort, and the PCBoard.sys in place has Sysop access! This insures no one gets accidental Sysop access, which could occur if the system had a boot in the middle of the session. This same situation is true of any door, or exit to DOS, usually trusted to the DTR check. If you have a first STARTUP.BAT that runs after the AUTOEXEC.BAT upon boot, you may like to use such a line to clear the 2nd account PCBoard.sys and any PCBoard.sys accessible even in a first account where loss of carrier detect will not clear it, as, if you allow Local logons this is possible also. This "empty" PCBoard.sys isa clean alternative to checking for a User's Password upon return to the board from a door. Using the "dummy PCBoard.sys" is required if you allow the User to exit the BBS from within the Second Account. If you do not allow it, and the User drops carrier, PCBoard will properly recycle, and reload the first account, which will then also recycle due to carrier loss. While this is slow, it is not insecure unless you have Users without modem use. You may choose to create a command called "OFF" to allow Users to exit the BBS from the Second Account to quickly restore the BBS online. See the information on this command later. That is basically what is required in the Door calling the second PCBoard to load. You will have to include all the other checks used as necessary, if you plan to open doors, run an event, etc. from the second PCBoard loaded. SECOND.BAT - this file is not required unless you choose to run a door from within the second account, and it then must be used to reload the second account. Notice where it is called in the SECOND file, which is copied over to a DOOR.BAT by PCBoard when the second account is accessed. This means you do have the alternative of insteading loading the DOOR.BAT found in the first account sub-directory, but I believe you will find this method cleaner. if exist endpcb del endpcb if exist door.bat del door.bat c:\pcb\pcb145 :done if exist door.bat door if exist event.bat event if exist endpcb goto end second :end copy pcbsys.hld pcboard.sys c: cd\pcb board Notice that it should appear identical to your BOARD.BAT file you use for the first account, except that it will reload itself if the ENDPCB file is not found. Your BOARD.BAT should call BOARD in that case, as the first account always reloads if no ENDPCB is found, as both the first & second accounts then assume you are returning from either a Door or the daily Event. ANYDOOR - example of a generic door loading file, PCBoard will copy the contents to a DOOR.BAT when the ANYDOOR is called. The ANYDOOR must be the actual name of the Door being called listed in the DOORS.LST file. This example is meant to run ANYDOOR from the second account, then return to the second account after exiting. cd\doors mydoor c: cd\pcb\second second This is assuming you created the SECOND.BAT, rather than reloading from the first account DOOR.BAT still sitting in the first account sub-directory. 2ACT.NAM: ASCII file of 52 byte records, holds User names for 1st account and second account, and flags for LOCK and ALLOW for each. Note: The following applies to the ver.2.0 file, though the first 3 records are not used by 2ACT or 2ACTSM until the 3.0 release. First 3 records hold User names of Users allowed to change their logon names into Second Account for maintenance reasons - the second half of each such entry is their password to enter 2ACT maintenance. The LOCK and ALLOW flags are ignored in those records, as those Users are given the option of either maintenance or access every time 2ACT is accessed, and those Users must have a separate entry for alias use also - upon such User choosing to access the second account, the record with the alias is used. Note: At this time, 2ACTSM.EXE can only be run locally or through the use of DOORWAY over the modem, and does not recognize the first three entries in any manner. Under Sysop maintenance, the LOCK flag can be set on/off for any User registered in the .NAM file. The Sysop can create a record and LOCK any User regardless of whether he/she has a record in the PCBoard Users file. This file is created when 2ACTCVT is run. This 2ACT.NAM file MUST be created prior to running 2ACT. See the information on running 2ACTCVT. 2ACT.CFG This file must be located in the directory from which @ACT is called, and contains all needed filenames and flags for 2ACT. Line 1 - drive, path, filename of first account PCBoard.sys Line 2 - drive, path, filename of first account USERS file Line 3 - drive, path, filename of 2nd account PCBoard.sys Line 4 - drive, path, filename of 2nd account USERS file Line 5 - drive, path, filename of 2nd account PWRD file Line 6 - drive, path, filename of CALLERS file to log info Line 7 - drive, path, filename to create NOGOOD file Line 8 - drive, path, filename of message if NOGOOD created Line 9 - drive, path, filename to create NEWGUY file Line 10 - drive, path, filename of message if NEWGUY created Line 11 - command to load PCBoard Line 12 - drive, path, filename of 2ACT.NAM file Line 13 - LOCK feature - MUST be Y, N or ALL Line 14 - drive, path, filename of message if User LOCKed. out Line 15 - ALLOW feature - MUST be Y, N or ALL Line 16 - drive, path, filename of message if User not ALLOWed Line 17 - drive, path, filename to create 1STTIME file Line 18 - Reserved until version 3.0 - MUST be set to N Line 19 - Reserved until version 3.0 - MUST be set to N Line 20 - Reserved until version 3.0 - MUST be set to N Line 21 - Reserved until version 3.0 - MUST be set to N Line 22 - Name of your BBS, for display on entry Line 23 - Registration number The first 6 lines are self-explanatory. 2ACT must know where to locate all access PCBoard files. It is allowed to use the same files for both first and second accounts if so required. Line 11 - this is written to the BAT file that loads the second PCBoard account, and would normally be just: c:\pcb\pcb145 It is included only so you have the option of placing any switches required by you on this line Note: Do NOT place any modem control switches (C:##, ERR) or an error will occur Line 12 - most likely, c:\pcb\second\2act.nam - where all User info required to access Second Account is stored Line 13 - LOCK line - MUST be N, Y or ALL This allows turning on/off the flag placed in the .NAM file to lock-out a User from being effective - and the method of handling New Users not listed in the .NAM file. It is also important when running 2ACTCVT.EXE and 2ACTADD.EXE - please see the references under those headings. Set to Y: LOCK parameter in use - The LOCK flag of the .NAM file will be checked for all Users before allowing access. If the User flag in .NAM is set to Y, the User is exited, with no explanation. If the User flag is set to N, the User is not locked out, and PCB2ACT allows the second account to be loaded. Set to N: LOCK parameter is disabled, all Users have access based on other parameters set, even if they are flagged as LOCKed Set to ALL: If set to ALL, every User is assumed to be LOCKed out of the second account, unless they already have a valid entry (without the LOCK set to Y) in the .NAM file. If set to ALL, it is assumed a relatively small number of users have access to the Second Account (or Sysop maintenance would be a lot of work!), so the .NAM file is searched BEFORE sending the notice to the User that the Second Account is loading. If no entry exists for the User, Second Account exits with no message. It is suggested you alter the PCBTEXT file (Record 549) no say nothing to the User if you use the ALL feature. Then the User will get no display whatsoever of the attempt to load the Second Account if he has not previously been given access. Line 14 - if a User is LOCKed out, either because of Line 13 being set to ALL, or his LOCK flag set by the Sysop in 2ACT.NAM, this file will be displayed to the User. Note: placing any single character (preferably N) in this line means NO message will be displayed Line 15 - ALLOW line - MUST be set to Y, N or ALL This controls how Users are handled, generally New Users into the Second Account. Set to N: Flag which can be set by the Sysop in 2ACT.NAM is ignored entirely Set to Y: Only Users with the ALLOW flag set to Y in the 2ACT.NAM file are allowed in. This does not stop anyone with no record from entry. New Users placed with an N in their ALLOW flag. Set to ALL: Same as Y, but, when 2ACTADD places a New User, this will set the Users ALLOW flag to Y. Line 16 - if a User is not ALLOWed, by his ALLOW flag, this file will be displayed to the User. Note: placing any single character (preferably N) in this line means NO message will be displayed Line 17 - file to be created the first time a User enters each day If set to N, no file is created Lines 18 to 21 are currently reserved, and portions of their parameters are already included in the version 2.0. These lines MUST be set to N at this time, or unpredictable actions may occur. These lines will be used to control additional functions of time control, maintenance, and files display in the future. Line 22 - your BBS name as you wish it to appear upon Second Account entry Line 23 - registration number for your BBS only Placing any value other than one assigned to you will result in it being ignored 2ACTADD.EXE This MUST be run to add a User to the 2ACT.NAM file. Usually called from the same BAT file that called the second account, it will read the last User record of the second account USERS file and check for an entry of that User in the 2ACT.NAM. If no entry exists, the new entry is made. The LOCK flag will not be set, and the ALLOW flag will be set based upon the parameters the Sysop placed in the ALLOW line of the 2ACT.CFG. The Sysop can choose to enter any User with 2ACTSM instead, but most likely, with the possiblities covered for New Users via the flags specified in the 2ACT.CFG, this program will be able to handle the situation you have common to your BBS. NOGOOD This file is built when 2ACT is unable to decide how to handle a user for some reason, and exits back to the first account. It is written only in case the Sysop has a reason to check at another level for access to the second account. It can be checked for in the BAT file if the Sysop requires it for other use. This filename can be changed to whatever you require by entry in the 2ACT.CFG file. NEWGUY This file is built when no account if found for the user in the 2ACT.NAM file. Its existence means the user will not have a PCBOARD.SYS file written for him, and must enter the second account as a New User. If you choose, this can be used to call other programs you may need to run. It is expected you will use a check for this file to run the 2ACTADD.EXE to place the users alias in the 2ACT.NAM file when he exits the second account. If you choose not to use it for that purpose, remember the user will again register in the second account the next time he tries if no entry is made. I do not suggest ignoring NEWGUY. 2ACTCVT.EXE This utility is provided for anyone previously having been using the old version of 2ACT which read User information from the Sysop maintained Comment 2 of the USERS file. Based upon the 2ACT.CFG file, it will construct the 2ACT.NAM file with what should be acceptable for your use. This program will write the first 3 records of the 2ACT.NAM file as names of a series of "X"s. Those fields are reserved for a future release of the 2ACTSM maintenance program. 1STTIME This file is created if the User is entering for the first time since midnite that day. It is useless unless PCB 14.5a (or newer) is in use which allows stuffing keystrokes into a PCBSTUFF.KBD file. It also allows forcing a display to the User upon return from a door by placing the file to be displayed in a file called PCBDOOR.TXT. Either way, a file to force keystrokes or a display is meant to be copied over by the "if exist" in the BAT file. Board Files: When you set up the second account, it is assumed you have created separate sub-directory for that account, and certain files in there are not shared with the first account. All other files should be the same as the first account. Some suggestions are shown elsewhere in this documentation. It is suggested you make several changes to your PCBTEXT file to be used in the Second Account - such as a change to the initial logon for a New User of the Second Account to insure he is prompted for an alias; also, it is a good idea to change the Main Command prompt to add a word to let the User realize he is in the Second Account; I made a few more changes - please review the enclosed version for ideas. PCBTEXT suggestions for the Second Account loaded: (this represents the enclosed PCBTEXT changes from 14.5a release copy) Record #: New prompt: 1 Leave a comment for the Adult Sysop (Enter)=no 2 Your FULL REAL NAME 4 Time Limit Exceeded in Adults Board @FIRST@ 8 Access Denied - This is a Private Conference @FIRST@ 11 Sorry, @FIRST@, New Users are entered by the SYSOP ONLY 12 Security Violation(s) - Returning to Main Board! 28 Automatic Lock-Out done! User removed from Adults Area! 53 (R) to re-enter your ALIAS or (C) to continue logon with NEW ALIAS 54 Do you wish to register your ALIAS now? (Enter)=yes 61 has nothing to do with 2ACT, but Users like it 61 (@BYTESLEFT@ left) Filename to Download (enter)=none 86 Pack the Adult User's file (enter)=no 118 shown if Alias is listed in TCAN file 118 Sorry, @FIRST@, only Proper Aliases are allowed ... 166 Now leaving the Adults Area @FIRST@! 192 Minutes Used Here: @OPTEXT@ 259 First name of Alias 260 Last name of Alias 396 (@X0C@TIMELEFT@@X0E min. left) @INCONF@ (Adults) Command 579 Paging the Adult Sysop For the PCBTEXT of the First Account, to be "seamless" to enter 2ACT, I suggest one change. Create an empty file (I called mine nuthin.) and edit record 594 to be: %c:\pcb\gen\nuthin and then no "Loading ADULTS..." is displayed, but some may choose not to do this at this time. A future release of 2ACT will be ENTIRELY SEAMLESS (nodisplays), and you may enjoy that at that time. PCBOARD.DAT - Several lines of your Second Account PCBOARD.DAT file must be set as follows: Modem Information - Modem Initialization String, leave blank Modem Offhook String, leave blank Reset Modem During Recycle, N Modem Off-hook during recycle, N Leave DTR up at Drop to DOS, Y Options # 1 - Exit to DOS after each Call? Must be Y to recycle properly Failure to set the "Exit to DOS" to "Y" can result in the wrong flagging within the USERNET.DAT file by PCBoard. The BRDM file normally used for the Main Menu should have one major change. Unless you chose to add a couple lines in the calling BAT file to remove the "good" PCBoard.sys written by the first account and force the User to exit the system after leaving the second account, he will be returned to the first account upon entering a G. The menu should reflect this (noticeably!) as "(G)o back to Main Board" in some manner. The you may wish to use a different TCAN file on the second account, as you may be more lenient (or strict) on that account. The PCBoard CALLERS file defined by Sysop in the .CFG file will log all important, or strange occurrences. This includes all new User access, all errors, and all maintenance changes. For files, if you have different files areas in the 2 accounts, you may wish to use a different Download.txt file for the second account, as this may greatly speed up searches (Prowho), and give more accurate figures if you use a utility that posts activities of the BBS. If you wish to allow Users to leave the BBS from the Second Account it is best to create a Door called OFF. If you have made the other changes to PCBTEXT and the BRDM, it will appear to be a command to the Users labelled OFF - just include it in the BRDM and then define it in the Doors.lst file. OFF This will be copied to the Doors.bat by PCBoard when invoked by the User, and its only purpose is to copy the PCBSYS.HLD to BOTH the first and second account PCBoard.sys files. You may wish to reconsider allowing this however, as it may not serve your purpose at this time. If you chose to run the time in the Second Account concurrent with the time in the first account, the User logging off using OFF will NOT get his USERS record updated with that Second Account time subtraction. copy pcbsys.hld pcboard.sys copy pcbsys.hld \pcb\pcboard.sys cd\pcb board Errors: The 3 potential errors are either that the BRUN45.EXE cannot be located in the path, the 2ACT.CFG file is missing a needed line, or 2ACT cannot find a file listed in 2ACT.CFG because of a typo. Be sure the filenames in the 2ACT.CFG are the same filenames defined in your PCBSetup for the PCBoard.sys, Users, and Pwrd files. In the event of an error that 2ACT cannot handle, NOGOOD is created, and the User returned to the first account. The most common reason for this is the Sysop removing the User from the USERS file of the Second Account, but fails to delete the User from the 2ACT.NAM file. This causes no problem, but the User will not understand what has happened. Maintenance: Presently, maintenance is done using 2ACTSM.EXE and no checking of who is accessing it is used. DOORWAY is required for maintenance online. The 2ACTSM allows you to perform all possibly required functions upon the 2ACT.NAM file holding the names and flags of the users for the Second Account of the 2ACT.CFG file being processed. 2ACTSM must be called from within the sub-directory holding the 2ACT.CFG of the Second Account to be managed. All edit and flag toggle functions are written immediately to the 2ACT.NAM file, not upon exiting the program. Important Note: The first 3 entries of the 2ACT.NAM should NOT be altered. They are presently not used by 2ACTSM, but will be in the future to allow online management to 3 users, and those records cannot get in to the Second Account if those records are used for that purpose. Prior to accessing 2ACT, 2ACTSM MUST be run to properly initialize the 2ACT.NAM file! Available commands for maintenance: (A)llow flag toggle This will reverse the current ALLOW flag setting of the current User record displayed (D)elete current User This will blank the "First Account Name", removing the current user from access. It does not release the the "Second Account Name". If (P)ack is not used after deleting an account, the "Second Account Name" cannot be reassigned by 2ACTADD if a New User entering Second Account chooses to use that name. 2ACT would treat any User later logging in with that Second Account name as a New User, and they would be forced to log on using all the normal PCBoard prompts when accessing the Second Account. (E)dit current User This makes the current record available for change, and you are prompted to change the First and Second Account names. The "Second Account Name" must have an entry, or the NOGOOD file will be created when the User enters, and no Second Account access will be available. The LOCK and ALLOW flags will always be either Y or N. Use the A and L toggles to alter these entries. (F)ind Second Account name Search for User record by "Second Account Name" (L)ock flag toggle This will reverse the current LOCK flag setting of the current User record displayed (N)ew User entry Lets Sysop create a new record, and prompts for first & second account names, and LOCK & ALLOW flag types. (P)ack file Used to remove all deleted Users, it will create a 2ACT.BAK and rewrite the 2ACT.NAM minus deleted Users (Q)uit Exits the program (S)earch for First Account Name Search for User record by "First Account Name" (##) locate record number ## Displays the record number entered. Entering a non-existing record number results in the first available record being displayed. (O)utput list to printer Prints all records to the standard printer defined in the 2ACT.CFG. (P)ack 2ACT.NAM file This is used to delete empty records, and can speed access if many empty records exist. (S)econd account name search Search for User record by "Second Account Name" (X)pert menu toggle Toggles you between full menu, and a single line prompt. (#) find record number Entering any number places you at that record number, but, will place you at record 1 if an invalid number entered Applications: The following will show the combined effect of the LOCK and ALLOW flags in the 2ACT.CFG and each User's LOCK and ALLOW flags. In all cases shown, it is assumed the Sysop has messages defined for LOCKed out and NOT ALLOWED Users. Leaving a single character for either of these message filenames within the 2ACT.CFG will result in no message file display in that case. In the unregistered version, a message must be available in either case. In the following the "*" shows treatment of New User by 2ACTADD. 2ACT.CFG set as: with 2ACT.NAM check result being: LOCK=N, ALLOW=ALL New User w/o record - New User allowed, User entry should be placed in BAT file by check of NEWGUY with Used to allow any 2ACTADD.EXE User in without any checks by the * New User will be entered with flags Sysop/Co-Sysop of: required. LOCK=N and ALLOW=Y User w/LOCK=Y or w/LOCK=N - LOCK ignored w/ALLOW=N - User displayed NOT ALLOWED message, returned to first account w/ALLOW=Y - normal access to account LOCK=N, ALLOW=Y New User w/o record - New User allowed to enter, but, it is assumed he is to be assigned a level by PCBoard that doesn't allow any privileges User entry should be placed in BAT file by check of NEWGUY with Used to let Users 2ACTADD.EXE register, but needs Sysop/Co-Sysop * New User will be entered with flags to set ALLOW flag of: LOCK=N and ALLOW=N User w/LOCK=Y or w/LOCK=N - LOCK] ignored w/ALLOW=N - User displayed NOT ALLOWED message, returned to first account w/ALLOW=Y - normal access to account LOCK=N, ALLOW=M New User w/o record - New User allowed User entry should be placed in BAT file by check of NEWGUY with 2ACTADD.EXE * New User will be entered with flags of: LOCK=N and ALLOW=Y by 2ACTADD.EXE User w/LOCK=Y or w/LOCK=N - LOCK ignored User w/ALLOW=Y or w/ALLOW=N - ALLOW ignored User w/record is allowed normal account access LOCK=Y, ALLOW=ALL New User w/o record - New User allowed User entry should be placed in BAT file by check of NEWGUY with 2ACTADD.EXE * New User will be entered with flags of: LOCK=N and ALLOW=Y by 2ACTADD.EXE w/LOCK=Y - User displayed LOCKED OUT message and returned to first account User w/LOCK=N and: w/ALLOW=N - User displayed NOT ALLOWED message, returned to first account w/ALLOW=Y - normal access to account LOCK=Y, ALLOW=Y New User w/o record - New User allowed, User entry should be placed in BAT file by check of NEWGUY with 2ACTADD.EXE * New User gets no entry in 2ACT.NAM w/LOCK=Y - User displayed LOCKED OUT message and returned to first account User w/LOCK=N and: w/ALLOW=N - User displayed NOT ALLOWED message, returned to first account w/ALLOW=Y - normal access to account LOCK=Y, ALLOW=N New User w/o record - New User allowed, User entry should be placed in BAT file by check of NEWGUY with 2ACTADD.EXE * New User gets no entry in 2ACT.NAM w/LOCK=Y - User displayed LOCKED OUT message and returned to first account User w/LOCK=N and: User w/ALLOW=Y or w/ALLOW=N - ALLOW ignored, User w/record is allowed normal account access All formats with LOCK=ALL prevent any access from any User not entered by the Sysop. Combined with the PCBText change, and the intentional non-mention of the Door in the DOORS file, the User is returned to the first account within seconds of entering the command to load the door with no explanation. It is suggested that the Sysop may choose to make the LOCKED.MSG read simply: (2ACT) is a Bad Command - Need (H)elp? which will effectively make any unregistered User feel the 2ACT does nothing. LOCK=ALL, ALLOW=ALL New User w/o record - New User is returned to first account, displayed LOCKED.MSG If no LOCKED.MSG exists, the User sees nothing in the registered version * 2ACTADD should not be run for New Users, but if run assigns LOCK=Y AND ALLOW=Y This configuration is used to not allow any User w/LOCK=Y - User displayed New Users except via LOCKED.MSG and returned to first Sysop entry account This literally "hides" User w/ LOCK=N and: the Second Account w/ALLOW=N - User displayed the NOT ALLOWED message and returned to first account w/ALLOW=Y - access to account LOCK=ALL, ALLOW=Y New User w/o record - New User is returned to first account, displayed LOCKED.MSG If no LOCKED.MSG exists, the User sees nothing in the registered version * 2ACTADD should not be run for New Users, but if run assigns LOCK=Y and ALLOW=N This configuration is used to not w/LOCK=Y - User displayed LOCKED allow any New OUT message and returned to Users except via to first account Sysop entry - it User with LOCK=N and: literally "hides" w/ALLOW=N - User displayed NOT the sub-board. ALLOWED message, returned to first account Same as above. w/ALLOW=Y - normal access to account LOCK=ALL, ALLOW=N New User w/o record - New User is returned to first account, displayed LOCKED.MSG. If no LOCKED.MSG exists, the User sees nothing in the registered version * 2ACTADD should not be run for New Users, but if run assigns LOCK=Y and ALLOW=Y This configuration is used to not w/LOCK=Y - User displayed LOCKED allow any New OUT message and returned to Users except via first account. Sysop entry - it literally "hides" w/LOCK=N and: the sub-board. User w/ALLOW=Y or w/ALLOW=N - ALLOW ignored Same as above, but User w/record is allowed normal no ALLOW function. account access Questions and Answers The following are the questions previously asked by Sysops using Second Account: Q: The modem hangs up on the user as soon as 2ACT runs. Why? A: 2ACT performs no modem controls, neither should anything else loaded after it runs. Review the modem initialization settings in the second PCBOARD.DAT loaded, the second copy should do nothing. Be sure you are using a DTR patched copy of BRUN45.EXE Q: The user's time online comes straight from the PWRD file, and doesn't reflect time used. A: This is only true on first entry, when the user must fill out his new informaiton. After that, time used is in the PCBOARD.SYS file, and is not altered by 2ACT. It is suggested you create a lower level for new users accessing the 2ACT for the first time, allowing only a short time in on that first logon. This is expected if a Sysop is using it for adult access, as he is expected to confirm the user being allowed prior to higher access. An alternative method will be considered for a future release, as the Sysop may use 2ACT to prevent further access, which is most likely what you have decided to do.